Real-time messaging method and apparatus

ABSTRACT

A system and method for the late-binding of time-based media in real-time. With late binding, the sender may create time-based media before or at the same time an active delivery route to the recipient is discovered. As soon as the route becomes available, the media is transmitted. The existing DNS and email infrastructure is possibly used for route discovery, while any real-time transmission protocol may be used for the actual delivery of the media. “Progressive” emails may also be used for the real-time delivery of time-based media.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.15/923,869 (P020FC6), filed on Mar. 16, 2018. U.S. application Ser. No.15/923,869 is a Continuation of U.S. application Ser. No. 15/710,627(P020FC5), filed on Sep. 20, 2017. U.S. application Ser. No. 15/710,627is a Continuation of U.S. application Ser. No. 15/233,325 (P020FC3),filed on Aug. 10, 2016, now U.S. Pat. No. 9,800,528. U.S. applicationSer. No. 15/233,325 is a Continuation of U.S. application Ser. No.15/091,746 (P020FC2), filed Apr. 6, 2016, now U.S. Pat. No. 9,634,969.U.S. application Ser. No. 15/091,746 is a Continuation of U.S.application Ser. No. 14/839,266 (P020FC1), filed Aug. 28, 2015, now U.S.Pat. No. 9,338,113, which is a Continuation of U.S. application Ser. No.12/857,486 (P020F), filed Aug. 16, 2010, now U.S. Pat. No. 9,178,916.U.S. application Ser. No. 12/857,486 (P020F) is a Continuation-in-Partof U.S. application Ser. Nos. 12/419,861 (P020A), 12/419,889 (P020B),12/419,914 (P020C), 12/552,979 (P020D), now U.S. Pat. No. 8,688,789, and12/552,980 (P020E), now U.S. Pat. No. 8,645,477, each claiming priorityof U.S. Application No. 61/148,885 (P020P) filed Jan. 30, 2009. U.S.application Ser. No. 12/857,486 (P020F) is also a continuation-in-partof U.S. application Ser. No. 12/028,400 (P001), filed on Feb. 8, 2008,now U.S. Pat. No. 8,180,029, which claims priority of U.S. PatentApplication Nos. 60/937,552 (POOH') filed on Jun. 28, 2007 and60/999,619 (P001P2), filed on Oct. 19, 2007. All of the above-listedapplications are incorporated herein by reference for all purposes.

BACKGROUND Field of the Invention

This invention pertains to communications, and more particularly, to alate binding communication system and method for real-time communicationof time-based media.

Description of Related Art

Currently there are three globally used addressing domains. The postalsystem, which is mainly used for the delivery of letters and parcels,relies on the use of a physical address, such as a house address, officebuilding address or Post Office (PO) box. In order to assure thedelivery of a letter or parcel, the physical address of the recipientmust be provided, including a country, state or territory, a city ortown, postal or zip code, street name and street number. The existingtelephone infrastructure defines another global addressing domain thathas historically been used for near real-time voice communications(i.e., telephone calls). Both land-line and mobile telephones areaddressed (i.e., called) using a telephone number, which typicallyincludes a country code and a variable number of additional digits toidentify a particular phone within a given country and/or area code.When a circuit connection is made between the calling parties, a fullduplex conversation may take place. A third global addressing system isemail. Every email account is identified by a unique globallyaddressable email address, which defines a user name and a domain name.

Emails are typically text messages that are sent from a sender to one ormore recipients. The emails are created on an email client. Onewell-known email client is Microsoft Outlook, which is used to create,receive and manage email messages on a computer. Alternatively, freeemail services like Yahoo, Google or Hotmail are available to usersthrough a web page. Regardless of the type used, an email client willtypically (i) list or display all the received messages, with an emailheader showing the subject of the email, the sender of the email, thedate/time it was sent and possibly other attributes such as the size ofthe email; (ii) allow the user to select messages for review; (iii)allow the user to type and send new messages to recipients and reply tothe received emails of others; and (iv) allow attachments, such as stillphotos, documents, or video clips, to be attached to an out-going email.

An email message must first be created in full before it can be sent. Asender will typically first define a recipient by entering their emailaddress into the appropriate “To” field in the header of the email. Thetext message is then typed into the body of the email and files mayoptionally be attached. When the message is complete, the user sends theemail. During the send sequence, the email client initiates a sessionwith its email server located on a network. This session is typicallyestablished with the Simple Mail Transport Protocol (SMTP). During thesession, the email client provides the SMTP server with the emailaddress of the sender, the email address of the recipient, and the bodyof the email with any attachments. The email addresses of the recipientis segmented into two parts, including the recipient's name (e.g.,“jsmith”) and the domain name (e.g., “hotmail.com”). If the recipient isin a domain that the SMTP server controls, then the server carries outdelivery instructions for the specific recipient, which is typicallydelivery of the email to an in-box associated with the recipient on thesame SMTP server or another server located in the same domain. On theother hand if the recipient is in a domain that the server does notcontrol, then the email server needs to communicate with a server thatcontrols the recipient's domain using SMTP.

To send the email to the recipient in another domain, the SMTP serverinitiates a conversation with the Domain Name System (DNS), asking forthe Mail eXchanger (MX) record of the recipient's domain. This MX recordcontains a prioritized list of SMTP servers for that domain. The emailis then sent from the SMTP server of the sender to the first SMTP serverin the MX list that responds. This first responding server thendetermines if the recipient is in the domain the first responding servercontrols. If so, the email is delivered to the inbox of the recipient.If not, the above-described process is repeated until a respondingserver is the one that can deliver the message into the recipient'sinbox. Each server along the delivery route is sometimes referred to asa “hop”. Once in the inbox, the email may be accessed through the emailclient of the recipient, which may be located on the computer of therecipient or on the Internet. If an email is sent to multiple parties,the above-described process is repeated for each recipient.

The above-described sequence generally applies for emails sent over theInternet. With certain proprietary systems, such as an email sentbetween two Microsoft Exchange users on the same proprietary network,the SMTP protocol may not be used for routing the email but emailaddresses are still used. The operation of the proprietary protocol andserver is essentially the same as SMTP.

The existing email infrastructure, regardless if it relies on SMTP or aproprietary email protocol, is essentially a “store and forward”messaging system. An email message must first be created in its entiretybefore it can be sent. At the SMTP or proprietary mail server of thesender, as well as any intermediate email server hops along the path tothe SMTP or proprietary mail server of the recipient, the email messagemust be received in full before it can be forwarded. Finally the emailmust be received in full at the inbox of the recipient before therecipient can review the message.

By way of comparison, telephone conversations over the Public SwitchedTelephone Network (PSTN) are progressive in nature. As words are spoken,they are simultaneously transmitted from the sender to the recipient,where they are heard effectively live or near real-time. As a result,telephone conversations can be conducted in a “live” or near real-timemode through a common network connection (i.e., a circuit). Emailcommunication in contrast usually occurs through a series of separatestore and forward messages, often sent back and forth between two ormore parties at distinct times, across a network, such as the Internet.

It is well known to attach a file to an email containing time-basedmedia (i.e., media that changes with respect to time), such as a videoclip. The time-based media attached to an email message, however, cannever be reviewed by a recipient “live”, as it is being created, due tothe store and forward nature of email. Rather the email and theattachment containing the time-based media must first be created, sent,stored and forwarded at each email server hop on the network, and thenreceived by the recipient in full before the time-based media of theattachment can be reviewed. It is therefore not possible for therecipient of an email message to review the media in near real-time asthe media is being created.

Telephone messaging systems are also known where a voice message may becreated and sent to a recipient in the form of an email. With thesesystems, the Public Switched Telephone Network (PSTN) is used incooperation with emails. In use, a recording of the message must firstbe made, stored, and then forwarded to the recipient by email. Again,however, the message must first be received in full before the recipientcan review the recorded message.

Instant messaging or IM is another example of a store and forwardsystem. Similar to email as described above, messages must be completedbefore they can be forwarded to a recipient. Messages in IM systems aregenerally much shorter than those sent via email. Each line of text inIM systems is a separate message delivered in a store and forwardmanner. Existing IM systems do not provide a way for a recipient toprogressively and simultaneously review a message as the sender createsthe message.

“Live” text systems are well known, although they were mostly used onearly Unix systems with dumb terminal interfaces. These text systems,give the appearance of being “live” since each individual keystroke issent to the recipient as soon as the sender pressed that key. But inreality, these systems are actually store and forward based, where thetransmission of each keystroke is a discrete event. These systems arefor text only (i.e., non time-based media only) and they do not allowthe recipient to progressively review the media in real-time per se.

In the context of communications, a recipient address can be describedas “bound” when a valid delivery path across the network has beendetermined for that address. Conventional telephone calls over the PSTNare said to use “early binding” because the dialed phone number, the“recipient address” in this case, is used to establish some active path(i.e., a circuit connection) to the recipient before any media can betransmitted to the recipient. Only after the connection is made can thecaller begin speaking and the media transmitted. Regardless if the callis placed to one or more telephone numbers, or the call is transferredto a voice messaging system, the binding typically occurs before anywords can be delivered. Since the binding of the recipient's address toan active destination on the network happens before any transmission ofmedia, it is said to be “early”. In contrast, emails are said to employ“late” binding. A person may compose an email message and send it over anetwork without binding that message to the device on which therecipient will consume it. Instead, after the email is composed, theemail address of the recipient is used to route the email to therecipient to be reviewed on a device and at a time of the recipient'schoosing. Since late binding systems require the completion of a messagebefore it can be sent, late binding systems cannot be used for “live”communication.

SUMMARY OF THE INVENTION

The present invention solves many of the problems of the prior art byproviding a late binding communication system and method for real-timecommunication of time-based media. With late binding, a sender has theability to transmit time-based media before or at the same time as anactive delivery route over a communication network to the recipient isdiscovered. As soon as the delivery route becomes at least partiallyknown (i.e., the next hop), the sender may transmit available time-basedmedia. By providing both the sender and each server hop with the abilityto transmit available media as soon the next hop is discovered,time-based media may be transmitted to the recipient in real-time beforethe complete delivery route to the recipient is fully known. Latebinding thus solves the above-described problems, namely the (i) waitingfor a circuit connection to be established before communication may takeplace, with either the recipient or a voice mail system associated withthe recipient, as required with conventional telephony or (ii) waitingfor an email to be composed in its entirety before the email may besent.

In one non-exclusive embodiment, the invention uses the existing globaladdressing and routing infrastructure of email to support real-timecommunication of time-based media. With this embodiment, the senderdefines the email address of the intended recipient. As soon as theemail address is defined, a delivery route to the recipient isdiscovered using the existing DNS infrastructure and DNS lookup resultsof the email address. A real-time communication protocol is used for theactual delivery of the time-based media to the recipient as the deliveryroute is discovered.

In another non-exclusive embodiment, an email client that is capable ofsending “progressive” emails is used. Like conventional emails,progressive emails include a header that has one or more fields fordefining the email address for one or more recipients. Progressiveemails, however, differ from conventional emails in at least tworegards. With progressive emails, a delivery route to the recipient isdiscovered as soon as the email address of the recipient is defined,rather than after the body of the email is composed and the email issent. The body of progressive emails is dynamic, not static, as withconventional emails. Consequently as time-based media associated withthe email is created, it is progressively transmitted to the recipientusing the route discovered as soon as the email address of the recipientis defined. By further modifying the access protocols used incooperation with convention email protocols, the recipient may alsoreview the incoming time-based media of progressive emails in real-timeas the media is received. In variations of this embodiment, the emailclient may reside on a server or on a communication device of the senderand the progressive email may be delivered to an inbox associated withthe recipient located either at a server associated with the recipientand/or on the communication device of the recipient.

The invention may also be used in cooperation with a messaging systemwhere the time-based media of transmitted and received messages isprogressively stored as either as the media is created or receivedrespectively. With the progressive storage of time-based media, arecipient may review incoming messages either (i) synchronously in areal-time mode, (ii) asynchronously in a time-shifted mode and (iii)seamlessly transition the review of a message between the two modes. Inaddition, the messaging between two or more parties may be either halfor full duplex, the latter providing a user experience similar to aconventional telephone call. Another advantage associated with thestorage of created media is the ability to provide limited communicationcapabilities when the communication device of a user is disconnectedfrom the network. A user of a cell or mobile phone for example willoften roam into regions beyond network coverage, or into areas wherenetwork coverage is weak or non-existent. When this occurs, the user canstill create a message for a recipient while disconnected from thenetwork. When the user roams back into an area of network coverage, themessage is transmitted out of storage. The storage of media of incomingmessages also allows the recipient to review the messages from storage,in the time-shifted mode, when disconnected from the network.

In other embodiments, the sender and recipient may communicate over acommunication network using either a client-server model or apeer-to-peer model. In another embodiment, messages for a recipient maybe posted and accessed on a web server. In yet another embodiment,identifiers other than globally unique email addresses may be used foridentifying a recipient and for routing purposes. This invention istherefore not limited to the use of globally unique email addresses, butrather, may be used with any type of identifier.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by reference to the followingdescription taken in conjunction with the accompanying drawings, whichillustrate specific embodiments of the invention.

FIG. 1 is a diagram of an exemplary network capable of supporting liveor near real-time communication of time-based media between usersaccording to the principles of the invention.

FIG. 2 is a diagram of a first exemplary communication device accordingto an embodiment of the present invention.

FIG. 3 is a diagram of another exemplary communication device accordingto another embodiment of the present invention.

FIGS. 4A and 4B are flow diagrams illustrating one possible example ofthe sequence for creating an email header on a communication deviceaccording to the principles of the present invention.

FIGS. 5A through 5D are flow diagrams illustrating possible embodimentsof the sequence for conducting communication over a network inaccordance with the principles of the present invention.

FIG. 6 is a flow diagram illustrating an embodiment for the attachmentof a media file to an email in accordance with the principles of thepresent invention.

FIG. 7 is a diagram illustrating another embodiment for the delivery oftime-based media over the network in accordance with principles of thepresent invention.

FIG. 8 is a diagram illustrating the structure of a conventional emailaccording to the prior art.

FIG. 9 is a diagram of one possible embodiment of a progressive emailaccording to the principles of the present invention.

Throughout the Figures, like reference numbers refer to like elements.

The above-listed figures are illustrative and are provided as merelyexamples of embodiments for implementing the various principles andfeatures of the present invention. It should be understood that thefeatures and principles of the present invention may be implemented in avariety of other embodiments and the specific embodiments as illustratedin the Figures should in no way be construed as limiting the scope ofthe invention.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

The invention will now be described in detail with reference to variousembodiments thereof as illustrated in the accompanying drawings. In thefollowing description, specific details are set forth in order toprovide a thorough understanding of the invention. It will be apparent,however, to one skilled in the art, that the invention may be practicedwithout using some of the implementation details set forth herein. Itshould also be understood that well known operations have not beendescribed in detail in order to not unnecessarily obscure the invention.

I. The Use of the Email and DNS Infrastructure to Define the Routing forthe Delivery of Messages Containing Time-Based Media Using a NearReal-Time Communication Protocol for the Actual Delivery of the Media

Referring to FIG. 1, a diagram of a representative network systemcapable of (i) supporting “live” or near real-time communication oftime-based media and (ii) routing using the infrastructure of email andDNS according to one possible embodiment of the invention is shown. Thesystem 10 includes a network 12 with users A, B, C and D usingcommunication devices 14A, 14B, 14C and 14D and Servers 16A, 16B, 16Cand 16D located on the network 12. The network 12 further includes a DNSserver 18. In various embodiments, the network 12 may include theInternet, an intranet, a mobile IP network, or any other type of networkthat relies on the Internet Protocol and/or DNS, or any combinationthereof. Users A, B and C are each addressed by the servers 16A through16D by their respective globally addressable email addresses“UserA@Domain A”, “UserB@Domain B”, and “UserC@Domain C”. User D isintentionally not identified on the network 12 by a globally addressableemail address for reasons mentioned below.

The Servers 16A, 16B, 16C and 16D are each configured to provide one ormore services to Users A, B, C and D respectively. In this example,Server A defines Domain A and provides User A with the standard emaildelivery service using SMTP (or a similar proprietary or non-proprietaryservice) and MX DNS records, hereafter referred to as “MX”. Server Afurther provides User A with a real-time communication service,hereafter referred to as “RVX”. Server 16B defines Domain B and providesUser B with the real-time communication service RVX, but not the emailservice MX. Server 16C defines Domain C and provides User C with theemail service MX, but not the real-time domain RVX service. Server 16Ddoes not provide user D with either the real-time communication serviceRVX nor the email domain MX service, but possibly other services thatare not identified because they are not relevant.

In one embodiment, the real-time service RVX may rely on anycommunication protocol that allows users to communicate time-based mediain near real-time, but does not require the recipient to review thetime-based media in a near real-time mode. Known protocols with theseproperties include the Cooperative Transmission Protocol (CTP) describedin detail in the U.S. applications Ser. No. 12/028,400 and Ser. No.12/192,890 or the near real-time synchronization protocol of voice orother time-based media as described in U.S. application Ser. Nos.12/253,816, 12/253,833 and 12/253,842. The above-listed U.S.applications are assigned to the assignee of the present invention andare incorporated herein by reference for all purposes.

In alternate embodiments, the RVX service may rely on othercommunications protocols, individually or in combination, that providenear real-time communication, such as SIP, RTP, Skype, VoIP, etc.

The communication devices 14A through 14D may each be any type ofcommunication device, such as land-line telephones, VoIP telephones,cellular radios, satellite radios, military or first responder radios,mobile Internet devices, or just about any other type of communicationdevice. In addition, a given user might have multiple communicationdevices 14. For example, a user may have one or more of the following; ahome computer, a work computer, a Push to Talk radio, a mobile phone ora personal digital assistant (PDA). Regardless of the number ofcommunication devices 14 each user A, B, C and D has, each will operateessentially the same and receive the services provided by the servers16A, 16B, 16C and 16D as described herein respectively.

It should be noted that the system 10 as illustrated has been greatlysimplified compared to what would typically be implemented in actualembodiments. For the sake of illustration, the RVX and MX services as(or not) provided to Users A, B, C and D as listed above have beenpurposely selected to highlight and describe certain features andprinciples of the invention. In actual embodiments, however, there wouldlikely be a significantly larger number of users, each with one or morecommunication devices 14 and associated servers on the network 12,providing a variety of services to each user. In addition, anycombination ranging from a single server or a suite of servers 16 may beincluded on the network 12 to provide the RVX and/or MX for one tomultiple users respectively. The communication devices 14A, 14B and 14Cand the servers 16A, 16B and 16C may also communicate with one anotherin a manner similar to that described above using DNS, SMTP, or otherproprietary or non-proprietary email protocols for route discoveryacross one or more hops on the network 12.

The delivery route for a message to a recipient in the same domain istypically delivered to an inbox on the same server 16 or an associatedserver in the same domain. A message sent to a recipient in anotherdomain will typically be sent to the email server of the recipient viaone or more hops across the network 12. With each hop, the media istransmitted using the real-time protocol as soon as the delivery path tothe next hop is discovered. If multiple hops are required, then media istypically being transmitted between hops using the real-time protocolbefore the complete delivery route to the recipient is known (i.e., thepath through subsequent hops). This differs significantly fromconvention emails, where the body of the email is typically firstreceived in full and stored at each hop and forwarded to the next hoponly after the route to the next hop is discovered.

Referring to FIG. 2, a diagram of a communication device 14 according toone embodiment of the present invention is shown. In this embodiment,the communication device 14 is a mobile device 20 capable of wirelesslycommunicating with the network 12, such as a mobile phone or PTT radio.The mobile device 20 may optionally include one or more of thefollowing; a keypad 22, a display 24, speaker 26, microphone 28, volumecontrol 30, camera 32 capable of generating still photos and/or video, adisplay control element 34, a start function element 36 and an endfunction element 38. In various embodiments, the device 20 (i) is IPbased, meaning it is designed to communicate over the network 12 usingthe Internet Protocol and (ii) runs one or more RVX protocols, includingany of those listed above or any other near real-time communicationprotocol. In addition, the mobile device 20 may optionally also locallyrun an email client, access an email client located on one of theservers 16 located on the network 12, or be capable of both running andaccessing an email client on the network.

Referring to FIG. 3, a diagram of a communication device according toanother embodiment of the present invention is shown. In thisembodiment, the communication device 14 is a computer 40 connected tothe network 12, either through a wired or wireless connection (notshown). The computer 40 optionally includes one or more of thefollowing; a keyboard 42, a display 44, speakers 46, a microphone 48, acamera 50 capable of generating still photos or video, a mouse 52, astart function element 54 and an end function element 56. The computer40 is capable of running an email client, accessing an email clientlocated on the network 12, or both. In various embodiments, the computer40 (i) is IP based, meaning it is designed to communicate over thenetwork 12 using the Internet Protocol and (ii) runs one or more RVXprotocols, including any of those listed above or any other nearreal-time communication protocol. The computer 40 could be a portablecomputer, such as a laptop or personal digital assistant, and is notlimited to the desktop computer as shown. In addition, the computer 40may optionally also locally run an email client, access an email clientlocated on one of the servers 16 located on the network 12, or becapable of both running and accessing email client on the network.

The start function elements 36/54 and the end function elements 38/56 ofthe mobile device 20 and computer 40 are meant to be symbolic of theirrespective functions. It is not necessary for mobile device 20, computer40, or any other type of communication device 14, to physically includestart and end buttons per se. Rather, it should be understood that eachof these functions might be implemented in a variety of ways, forexample, by entering a voice command, a predefined keystroke or commandusing a touch screen or other input device such as a mouse, stylus orpointer, etc. In one specific embodiment, the start and/or end functionsmay be implemented by default. In other words, the start function mayautomatically be implemented by the creation of media after the emailaddress of a recipient is defined. For example, a sender may select arecipient from their contacts list, and then begin talking or creatingother time-based media. By virtue of defining the recipient and thecreation of media, the “start” function 34 may automatically beimplemented. Similarly, the end function may be implemented by default.After the sender stops creating media, the end function mayautomatically be implemented after a predetermined period of time.

In one non-exclusive embodiment, the network 12 uses the existing emailinfrastructure, including the globally recognizable email addresses ofthe recipient users and DNS for route discovery, while using a nearreal-time RVX protocol for the actual transport of messages containingtime-based media to the addressed recipient once the route isdiscovered. Like conventional emails, each message relies on a headerthat defines, among other things, a globally addressable email addressof one or more recipients for routing purposes. Unlike conventionalstore and forward emails, however, the time-based media of the messageis transmitted using a near real-time RVX protocol. As a result,time-based media may be simultaneously and progressively transmittedacross the network 12, as the sender creates the media. In addition, therecipient may optionally simultaneously and progressively render thetime-based media as it is received over the network.

When two or more parties are conversing (e.g., generating and reviewingtime-based media) at approximately the same time, the network 12 issupporting full-duplex, near real-time communication, using one or moreRVX protocol(s) for media delivery, while using the existing emailinfrastructure and DNS for routing. With full duplex real-timecommunication, the user experience is very similar to a conventionaltelephone conversation, except the hassles of dialing a telephone numberand waiting and listening to the phone ring while a circuit connectionis established is avoided.

Alternatively, if the recipient does not reply at approximately the sametime, then the user experience is similar to an asynchronous messagingsystem, such as voice mail, but again without the hassles of dialing thetelephone number of the recipient, listening to the phone ring while theestablishment of a circuit connection is attempted, and then theeventual rolling-over into the voice mail system of the recipient. Onthe contrary, the sending party simply has to select or otherwise definethe email address of the recipient and then start generating media. Themedia is routed to the recipient automatically without waiting for acircuit connection to be established.

Referring to FIG. 4A, a flow diagram illustrating one possible sequencefor creating and transmitting time-based media associated with a messageon a communication device 14 in accordance with the principles of thepresent invention is shown. If the user of a communication device 14wishes to communicate with a particular recipient, the user will eitherselect the recipient from their list of contacts or reply to an alreadyreceived message from the intended recipient. Alternatively, theglobally addressable email address of the recipient is manually enteredinto the device 14.

As soon as the email address of the recipient is defined, two operationsare performed. A message header is created (step 62) and the definedemail address is included in a header field (i.e., the “To”, CC, and/or“BCC” field). In addition, the route for delivering the media associatedwith the message to the globally addressed recipient is immediatelydiscovered using a DNS lookup result. The result can be either an actualDNS lookup or a cached result from a previous lookup. Thereafter, thestart function 36/54 is initiated, either manually or by default, andthe user may begin creating time-based media (step 64), for example byspeaking into the microphone, generating video, or both. The time-basedmedia is then progressively and simultaneously encoded (step 66),transmitted (step 68) over the network 12 using an RVX protocol usingthe discovered delivery route, and optionally persistently stored on thedevice 14 (step 70). It should be noted that although these steps 62through 70 are illustrated in the diagram in a sequence, for allpractical purposes, they occur at substantially the same time. As themedia is created, the RVX protocol progressively and simultaneouslytransmits the media across the network 12 to the recipient, as the routeis typically discovered without any perceptible delay to the sendinguser.

The time-based media of outgoing messages may optionally be persistentlystored on the sending communication device 14 for a number of reasons.For example, if time-based media of a message is created before thedelivery route is discovered, then the time-based media may betransmitted from storage when the delivery route at least to the nexthop is discovered. If time-based media is still being created after theroute is discovered, then the time-based media is transmittedprogressively and simultaneously as the media is being created.Alternatively with the storage of time-based media, the sender mayreview stored outgoing messages at an arbitrary later time. A messagemay also be created and stored when the communication device 14 is notconnected to the network 12, where connected is defined as the abilityto send messages over the network and not connected is defined as theinability to send messages over the network. When the device 14 laterconnects, the message may be transmitted to the intended recipient fromstorage, using either an RVX protocol or as an attachment to an email.

Referring to FIG. 4B, a flow diagram 100 illustrating one possiblesequence for creating a message header (step 62 in FIG. 4A) inaccordance with the principles of the invention is shown. In the step 62a, the globally addressable email address of the sender is provided inthe “From” field of the message header. In step 62 b, the globallyaddressable email address of the recipient is entered into the “To”field of the message header. If there are multiple recipients, the emailaddress of each is entered into the “To” field. In additionalembodiments, a “CC” or “BCC” field may be used for one or allrecipients. In step 62 c, a globally unique message ID or number isassigned to the message. In step 62 d, other information, such as aconversation name, or the subject of the message, is provided in theheader. In step 62 e, the start date/time the message was created andpossibly the end date/time of the message may be included in the header.In one embodiment, the steps 62 a through 62 e generally all occur atsubstantially the same time, with the possible exception of defining theend date/time. In other embodiments, the steps 62 a through 62 e mayoccur in any order. The start and end date/times ordinarily coincidewith the implementation of the start function 36/54 and end function38/56 on the sending device 14 respectively.

In certain embodiments, the steps 62 a through 62 e may be performed ona sending communication device 14. In other embodiments, the sendingcommunication device may send some or all of the message headerinformation to a server 16, where the steps 62 a through 62 e areperformed. The time-based media of the message may also be optionallystored on a server 16 for later review by the sending user ortransmission to the recipient.

In the embodiments described above, a message header with various fieldsincluding a To, From, Message ID number, Conversation Name, and messageStart and End time is provided. It should be understood that not all ofthese fields are necessary, and other fields may be included. The onlyrequired information is at least one recipient specified in one of theTo, CC, or BCC fields, which defines the globally addressable emailaddress of a recipient. The other fields are all optional.

The format of the message header is also variable. In one embodiment,the structure of the message header may be similar to that used withconventional emails or the enveloped used with emails. In otherembodiments, the structure of the message header may take any form thatis suitable for transmitting the globally addressable email address ofthe recipient(s), along with possibly other header information, acrossthe network 12. While specific email header fields are discussed forspecifying recipients, the actual header field containing the recipientaddress information may not necessarily include the globally addressableemail address of the recipient per se. As is well known in the art, an“envelope recipient” may be used to specify the email address of therecipient, even though the envelope recipient may differ from therecipients listed in the email headers. Thus as used herein, the termmessage header should be broadly construed to include both envelopeinformation and conventional message or email headers including anynumber of fields, such as but not limited to those specified in RFC 822or 5322. In addition, the usage of the terms “addressing” or “globallyaddressable email address” should be broadly construed to include anyaddressing method, including usage in conventional message or emailheaders or in a message envelope.

The network 12, under certain circumstances, may deliver messagescontaining time-based media that can (i) be simultaneously andprogressively transmitted to a recipient over the network 12 and (ii)reviewed in near real-time by the addressed recipient as the time-basedmedia is being created and sent by the sending user. Under othercircumstances, the messages cannot be delivered in real-time. Both thenear real-time and non real-time scenarios are discussed below withregard to FIGS. 5A through 5C respectively.

Referring to FIG. 5A a flow diagram 80 illustrating one possiblesequence for conducting near real-time communication with messagescontaining time-based media in accordance with the principles of thepresent invention is shown. The sequence is described in the context ofuser A sending a message to user B using any near real-time RVXprotocol. As noted above, server 16B provides user B with an RVXservice, but not the MX service. In this example, the steps 62 through70 as described above with regard to FIGS. 4A and 4B may occur either onthe communication device 14A of the sender or the server 16A.

In the initial step 82, server 16A receives the message header (or theheader information allowing the server to perform some or all of thesteps 62 a-62 e). As soon as user B's globally addressable email address(userB@DomainB) is received, server 16A requests that DNS server 18using standard DNS protocols perform a DNS lookup of domain B oraccesses a previously cached lookup for the RVX of domain B (step 84).Regardless of how obtained, the result is positive (decision 86) sincethe RVX exists for domain B. Typically at substantially the same time,the server 16A receives the time-based media of the message. As soon asthe delivery path to server 16B is at least partially known, the mediais progressively and simultaneously sent using the RVX protocol from theserver 16A to server 16B. The time-based media may be transmitted acrossone or more hops between the two servers 16A and 16B. At each hop, a DNSlookup result is used to discover the delivery route to the next hop,while the RVX protocol is used to deliver the time-based media to eachnext hop.

In one embodiment, the media is simultaneously and progressivelytransmitted to the communication device 14B of the recipient when thetime-based media arrives at server 16B. The recipient is notified of theincoming message, and in response, the recipient may elect tosimultaneously review the media in the near real-time mode as the mediaof the message is progressively received.

In an alternative embodiment, the media of the message is alsooptionally placed in an inbox and persistently stored on the recipientdevice 14B. With the persistent storage of the message, the recipienthas the option of reviewing the media in the near real-time mode as themedia is received or at an arbitrary later time from storage.

In yet another embodiment, the message may also be stored in an inboxlocated at the server 16B associated with the user B. In this manner,the user of device 14B may access the message in either real-time or atan arbitrary later time. As noted above, user B is not provided the MXservice and therefore cannot receive emails. But in situations whererecipient can receive emails, the message can be encapsulated into afile and the file attached to an email that is forwarded to the inbox ofthe recipient.

In yet other embodiments, the media of the message may be stored in anout-box of the sending user, either located on the user's sendingcommunication device 14A, or on the server 16A associated with thesender.

Referring to FIG. 5B, a flow diagram 80 illustrating one possibleexample of the communication sequence between user A and user C inaccordance with the principles of the invention is shown. As previouslynoted, server 16C provides user C with the MX service, but not areal-time RVX service. When user A wishes to communicate with user C,the initial sequence is essentially the same as that described above.Server 16A initially receives a message header (or the headerinformation necessary to optionally perform steps 62 a-62 e) with theglobally addressable email address of user C (userC@domainC) and theprogressive and simultaneous transmission of time-based media by user A(step 82). Since the RVX lookup result (decision 86) is negative, server16A performs a DNS lookup or uses a previously cached MX lookup fordomain C (step 90). With a positive result (decision 92), server 16Asends a conventional email with the time-based media encapsulated as anattachment (step 96) to server 16C. At the server 16C, the email isplaced in the recipient's inbox. The email may also be forwarded to aninbox on communication device 14C. Thus, when the recipient does nothave the RVX service, the time-based media of the message is sent acrossthe network 12 by Server 16A to server 16C, and possibly communicationdevice 14C, using the store and forward procedure of SMTP or a similarproprietary or non-proprietary email protocol.

Referring to FIG. 5C, a flow diagram 80 illustrating one possibleexample of the communication sequence between user A and user D inaccordance with the principles of the invention is shown. As previouslynoted, user D is not provided with either the email MX service or a nearreal-time RVX service. When user A wishes to communicate with user D,the initial sequence is essentially the same as that described above.Server 16A receives a message header with the globally addressable emailaddress of user D (userD@domainD) and the progressive transmission oftime-based media by user A (step 82). Since the RVX lookup (decision 86)and the MX lookup for domain D (diamond 92) are both negative, an errormessage is generated (step 94) and the message cannot be delivered (step96). In various embodiments, the time-based media of the message may bestored at either the sending communication device 14A, the server 16A,or both. The message may later be sent when the RVX and/or MX service isprovided to user D.

The scenario described with regard to FIG. 5C typically occurs if anincorrect email is provided for a recipient. When the sender attempts tosend a message using an invalid email address, the error message (step94) results. If the correct email address is provided, the message canthen be forwarded using either an RVX protocol or as an attachment to anemail using the MX service, depending on the services provided to userD.

In an alternative embodiment, the communication devices 14A through 14Cmay be arranged in a peer-to-peer configuration. With this arrangement,at least the sending communication devices 14 are capable of performingthe RVX and/or MX lookups on DNS server 18 directly and caching theresults, without the aid of an intervening server 16 to perform thethese functions. The communication devices 14 may also be capable ofprogressively transmitting the media of the messages directly to othercommunication devices. Depending on whether the recipient is a member ornot of the RVX and/or MX domains, the sending communication device 14Awill either (i) progressively transmit the time-based media of a messageto the recipient over the network 12 as the media is created; (ii)encapsulate the time-based media of the message into a file and transmitan email including the file as an attachment to the recipient using SMTPor a similar proprietary protocol; (iii) or receive an error message ifan invalid email address was used.

Referring to FIG. 5D, a flow diagram illustrating one possible exampleof peer-to-peer communication in accordance with the principles of theinvention is shown. In the initial step 101, a sending communicationdevice 14 indicates that it would like to communicate with a receivingcommunication device 14. In decision diamond 102, the communicationdevice 14 of the sender relies on either an actual or cached DNS lookupresult of the recipient's globally addressable email address todetermine if the peer recipient receives the RVX service. If the resultis positive, then the time-based media created (step 103) using thesending communication device 14 is progressively transmitted (step 104)to the recipient as it is created using the delivery route defined bythe RVX lookup. In decision diamond 105, it is determined if real-timecommunication is established. If yes, then the transmitted media isprogressively rendered at the communication device 14 of the recipientas the media is received (box 106). If real-time communication is notestablished, then the media of the message is placed in the inbox of therecipient (box 107), either on the device 14 of the recipient, a server16 associated with the recipient, or possible both. Real-timecommunication may not take place with the recipient for a number ofreasons, such as the recipient is not available, out of network range,or has indicated a desire to not review the message in the nearreal-time mode. In another alternative embodiment, the message mayalways be placed in the inbox of the recipient, regardless if it isreviewed in real-time.

On the other hand, if the recipient does not receive the RVX service(decision 102), then the media of the message is delivered by email,provided the recipient receives the MX domain service. The time-basedmedia is encapsulated into a file and attached to an email (step 108).When the message is complete, the email is transmitted using the routedefined by the MX lookup result (step 109) to the inbox of therecipient. In various embodiments, the inbox may be located on thedevice 14 of the recipient, a server 16 associated with the recipient,or both.

In situations where both peers are running an email client, media may besent in the form of an attachment to an email from the sendingcommunication device 14 to the receiving communication device 14. Thisdiffers from known telephone messaging systems, where a server, asopposed to a sending peer, emails a voice message to the recipient. Incertain embodiments, an attachment may be substituted or augmented by alink to a web page containing the time-based media, as described in moredetail below.

It should be noted that the discussion above with regard to FIGS. 4A, 4Band 5A through 5C has been simplified to illustrate certain aspects ofthe invention. It should be understood that actual implementations couldbe modified in several ways. For example, each time the server 16Areceived an email address, the server 16A would first determine if thedomain of the recipient (i.e., domain A, domain B or domain C), iswithin one or more local domains of the server 16A. If not, then theprocedures described above with regard to FIGS. 5A, 5B and 5C areperformed respectively. On the other hand if the domain of the recipientis within a local domain of the server 16A, then the server 16A maydeliver the message directly to the recipient either (i) in real-time ifthe recipient receives a real-time communication service or (ii) as anattachment to an email if the recipient receives the MX service, but nota real-time service. In addition, it may not be necessary for the Server16A to perform a DNS lookup in each instance. As is well known, previousDNS lookup results may be cached and used rather than performing a newDNS lookup each time an email address of a recipient is received.

Referring to FIG. 6, a flow diagram 110 illustrating one possiblesequence for sending time-based media encapsulated in an emailattachment in accordance with the principles of the invention is shown.When the time-based media of a message is to be sent in the form of anemail (e.g., box 98 in FIG. 5B or box 107 in FIG. 5D), the time-basedmedia generated by user A is first encapsulated in a file (step 112).The file is then attached to the email (step 114) when the message iscomplete. When the time-based media of the message is complete, theemail with the attachment is then transmitted (step 116) to the MXlookup result of the recipient in a manner similar to a conventionalemail.

With either the server or peer-to-peer models described above, the RVXlookup result is initially used to deliver the time-based media. If theRVX attempt fails, then the MX result is used as a backup. With thisarrangement, a conventional email with the time-based media included inan attachment and/or web link is used to deliver the media incircumstances where the recipient is not provided RVX service. The emailmay be created either on a server or on the sending device.

II. Delivery Options

Referring to FIG. 7, a diagram illustrating another embodiment for thedelivery of time-based media over the network 12 in accordance with theprinciples of the invention is shown. With this embodiment, the network12 is essentially the same as that described above with regard to FIG.1, with at least one exception. One or more of the servers 16A-16C areconfigured as web servers, in addition to providing the RVX and/or MXservices as described above. With this embodiment, users receive anemail from their respective server 16 containing a URL link when amessage is sent to them. When the user selects the link through a webbrowser running on their communication device 14, the appropriate webserver 16 serves up web pages allowing the recipient to access andreview the message. The served web pages may also provide a variety ofrendering options, such as review the media of the message in either thereal-time or time-shifted modes, catch up to live, pause a liveconversation, jump to the head of a conversation, jump to a previouspoint in time of the conversation, render faster, render slower, jumpbetween different conversations, etc. In the figure, the web serverfunctionality is provided as one of the services provided by servers16A, 16B and/or 16C. In an alternative embodiment, the web serverfunctionality can be implemented using one or more other dedicated webservers (not illustrated) on the network 12 besides 16A, 16B or 16C.

III. Email Protocol Modifications and Progressive Emails

The messages as described above are routed using globally addressableemail address and the DNS infrastructure for defining a delivery route,while using an RVX protocol for the actual delivery of the time-basedmedia in near real-time. Although the SMTP and other proprietary andnon-proprietary email protocols as currently defined and used areessentially store and forward protocols, with certain modifications,these protocols can be used as an RVX messaging protocol for the nearreal-time delivery of time-based media as contemplated herein. Withconventional emails, the media content must be composed in full andpackaged before the email can be sent. On the receiving end, the emailmust be received in full before the recipient can review it. Asdescribed in detail below, SMTP, Microsoft Exchange or any otherproprietary email protocol may be used for creating “progressive”emails, where media may be sent in real-time.

The existing email infrastructure can be used to support the real-timetransmission of time-based media by modifying the way the SMTP,Microsoft Exchange or other proprietary and non-proprietary emailprotocols (hereafter generically referred to as an email protocol orprotocols) are used on the sending side and modifying the way thatemails are retrieved from the server on the receiving side. Currentemail protocols do not strictly require that the entire message beavailable for sending before delivery is started, although this istypically how email protocols are used. Time-based media can thereforebe delivered progressively, as it is being created, using standard emailprotocols.

Email is typically delivered to a recipient through an access protocollike POP or IMAP. These protocols do not support the progressivedelivery of messages as they are arriving. However, by makingmodifications to these access protocols, a message may be progressivelydelivered to a recipient as the media of the message is arriving overthe network. Such modifications include the removal of the currentrequirement that the email server know the full size of the emailmessage before the message can be downloaded to the client. By removingthis restriction, a client may begin downloading the time-based media ofan email message as the time-based media of the email message isreceived at the server over the network.

Referring to FIG. 8, the structure of a conventional email 120 accordingto the prior art is illustrated. The email 120 includes a header 122 anda body 124. The header includes a “To” (or possibly the CC and/or BCCfields) field, a “From” field, a unique global ID number, a subjectfield, optional attachments, and a date/time stamp. The body 124 of theemail includes the media to be transmitted, which typically includes atyped message and possibly attached files (e.g. documents or photos).When complete, the email is transmitted by implementing a “send”function or command. A DNS lookup of the email address of the recipientis then performed and the email is routed to the recipient. Conventionalemails are “static”, meaning the body of the email, includingattachments, must be created before transmission may begin. Oncetransmission starts, the contents defined in the body is fixed, andcannot be dynamically altered or updated. As a result, there is no wayto progressively transmit with conventional emails time-based media asthe media is being created. Prior art emails 120 are therefore incapableof supporting near real-time communication.

Referring to FIG. 9, one possible embodiment of a “progressive” email130 according to the principles of the invention is shown. The emailmessage 130, which is capable of supporting real-time communication,includes a header 132 including a “To” field (and possibly CC and/or BCCfields) and a body 134. The structure of email 130 differs from aconventional prior art email 120 in at least two regards. First, theheader 132 includes an email Start date/time and an End date/time. Byassociating a start and end time with an email 130, as opposed to just adate/time stamp when an email 120 is sent, the second difference may berealized. As soon as the email address of the recipient is defined, thedelivery path to the next hop or hops is immediately ascertained, usinga DNS lookup result of the defined email address. Again, the lookupresult can be either an actual or a previous result that is cached. Asthe delivery route from hop to hop is discovered, time-based media maybe progressively transmitted as it is created, using the streamingnature of SMTP, Microsoft Exchange or any other type of email protocol.The body 134 of email 130 is therefore “progressive”. As the time-basedmedia associated with an email message 130 is dynamically created, thetime-based media is progressively transmitted to the email server of therecipient. If an email 130 is sent to multiple recipients, regardless ifidentified in the To, CC or BCC fields, the above process is repeatedfor each.

With progressive emails 130, an email protocol session is establishedwith the email server associated with the sender as soon as the emailaddress of the recipient is defined. This differs from conventionalemails 120, where the email protocol session is typically initiated onlyafter the email has been composed in full and the sender implements the“send” function. As a result, the delivery route can be discoveredeither before or concurrent with the progressive transmission oftime-based media as it is being created. In situations where thetime-based media may be created before the session is established, thetime-based media may be temporarily and/or persistently stored as themedia is created. The stored media may then be progressively transmittedfrom storage once the protocol session with the email server isestablished.

The End date/time of email 130 may be either defined or open-ended. Whenthe sender actively implements the end function 38/56 on thecommunication device 14, then the end time of the email 130 is defined.If the end function 38/56 is never implemented, then the duration of theemail 130 is “open-ended” and does not necessarily have a defined enddate/time. Open-ended emails 130 are therefore typically terminated bydefault after a predetermined period of time where no media is created.

In summary, progressive emails 130 can be sent using SMTP, MicrosoftExchange or any other proprietary or non-proprietary email protocol byimplementing the above-described modifications. Similarly, recipientsmay simultaneously and progressively review the time-based media ofprogressive emails 130 by modifying access protocols such as POP, IMACand the like. Together, these modifications enable the use of emailaddressing, email protocols, DNS and DNS protocols, and the existingemail infrastructure to support real-time communication of time-basedmedia.

IV. Late Binding of Recipient Addresses for Real-Time Voice and OtherTime-Based Media

With the messages (as described with regard to FIGS. 4A, 4B and 5A-5D)or progressive emails 130 described above, a user addresses a recipientusing their globally addressable email address and then immediatelybegins talking or generating time-based media. With each embodiment, thedelivery route is immediately discovered as soon as the email address ofthe recipient is defined. Time-based media is progressively transmittedalong the delivery route as it is discovered as the media is created.Consequently the discovery of an active delivery route and theprogressive creation, transmission and delivery of the time-based mediamay occur in real-time. In the event the actual delivery route isdiscovered after the creation of time-based media has started, then themedia may be temporarily and/or persistently stored and then transmittedfrom storage once the active delivery route is defined. No networkconnection or circuit needs to be established before the sender maystart talking or creating other media. The ability to progressively andsimultaneously transmit the time-based media using DNS and theinfrastructure of email therefore enables the late binding of recipientaddresses for voice and other time-based media in a manner thatpreviously was not possible.

V. Conversations

The messaging methods and systems as described (with regard to FIGS.1-3, 4A-4B, 5A-5D or FIG. 9) are each conducive for supportingconversations between sending and receiving users. When two or moreparties are conversing back and forth using any of the above-listed RVXprotocols or progressive emails 130, then the conversation may takeplace (i) in the near real-time mode; (ii) the time-shifted mode; or(iii) seamlessly transition between the two modes. When two or moreparticipants are conversing in the real-time mode, the user experienceis similar to a conventional full duplex telephone conversation. In thetime-shifted mode, the user experience is similar to an asynchronousmessaging system. As described in more detail in the above-mentionedU.S. applications, the media may be rendered using a number of differentrendering options, such as play, catch up to live, pause a liveconversation, jump to the head of a conversation, jump to a previouspoint in time of the conversation, render faster, render slower, jumpbetween different conversations, etc. By using certain renderingoptions, a user may seamlessly transition a conversation from thetime-shifted mode to the real-time mode and vice versa.

Regardless of the embodiment, the “reply” function may be implemented ina variety ways. For example, the recipient may enter an explicit replycommand into their communication device 14, such as by using apredefined voice or keystroke command, or entering a command through atouch screen. Alternatively, a reply message or email may be generatedautomatically when the recipient begins speaking or generating othertime-based media in response to a message or email 130. When a replymessage is automatically created, the email address of the originalsender is used for addressing the reply message.

In yet other embodiments, the RVX protocol used for sending andreceiving the messages of a conversation between participants in thereal-time mode do not necessarily have to be the same. For example, oneparticipant may send messages using one of the CTP, synchronization,progressive emails 130, VoIP, SIP, RTP, or Skype protocols, whereasother participants may use a different one of the listed protocols,provided some type of a common conversation identifier is used. Anymessages, regardless of the protocol used for transmission, are linkedor threaded together using the unique conversation identifier.

In various further embodiments, conversations can be defined using avariety of criteria. For example, conversations may be defined by thename of a person (e.g., mom, spouse, boss, etc) or common group ofpeople (e.g., basketball team, sales team, poker buddies, etc).Conversations may also be defined by topic, such as fantasy footballleague, ACME corporate account, or “skunk works” project. Regardless ofthe contextual attribute used to define a conversation, the ability tolink or organize the messages of a particular conversation togethercreates the notion of a persistent or ongoing conversation. With aconventional telephone call, the conversation typically ends when theparties hang up. There is no way to contextually link, organize andpossibly store the spoken words of multiple telephone exchanges betweenthe same parties. On the contrary, conversations, as defined herein, area set of common messages linked together by a common attribute. So longas messages are added to the conversation, the conversation iscontinuous or ongoing. This attribute makes it possible for aparticipant to contribute to a conversation at any arbitrary time. Forexample, a user may select a conversation among a list of conversationsand contribute a message to the selected conversation at anytime. Themessage is then sent to all the conversation participants. Messages aretherefore not necessarily sent when either a conversation is firstcreated or in reply to an incoming message.

VI. Implementation Embodiments

The messaging methods as described with regard to FIGS. 1-3, 4A-4B and5A-5D and progressive emails 130 may be implemented in a variety ofways. For example, cell phone and other mobile communication serviceproviders may provide users with peer-to-peer mobile communicationdevices that operate using either messages and/or progressive emails130. In addition, these service providers may also maintain a network 12of servers 16 for conveying messages between users as described hereinusing one or more RVX protocols.

In yet another embodiment, the messaging and progressive email 130methods may be embedded in a software application that is intended to beloaded into and executed on conventional telephones, mobile or cellulartelephones and radios, mobile, desktop and laptop computers. In each ofthese cases, the application enables the device to send, receive andprocess messages and progressive emails 130 as described herein.

In yet other implementations, conventional email clients can be modifiedto create, receive and process progressive emails 130. The modifiedemail client may alternatively reside on a server on the Internet orother proprietary or non-proprietary network, on sending or receivingdevices, or both.

Although the above-described systems and methods were generallydescribed in the context of a single sender and a single recipient (asdiscussed with regard to FIGS. 4A-4B and 5A-5D) or emails 130 to asingle recipient, it should be understood the messages and/or emails 130might be simultaneously sent to multiple parties. Each recipient willeither receive or not receive the message or email, depending on theirstatus, as described above.

Also although the above-described email methods were generally describedin the context of “globally” unique identifiers, such as an emailaddress, it is necessary to note that such identifiers do notnecessarily have to be a global. In alternative embodiments, theidentifier may uniquely identify a user within a defined non-globalcommunity of users. For example, a community, such a social networkingwebsite, may issue each user a unique identifier within the community.Users within the community can then communicate with one another, asdescribed herein with regard to FIGS. 1 through 10. The uniqueidentifier assigned to each user is used to not only authenticate eachuser, but also for routing messages and media between users. Accordinglythe term “identifier” as used in this application is intended to bebroadly construed and mean both globally and non-globally uniqueidentifiers.

It also should be noted that the system and methods as described hereinare not intended for use with only “live” real-time transmission. Theaforementioned systems and methods as described with respect to FIGS. 1through 3, 4A-4B, 5A-5D and 9 may also be used with the real-timetransmission of previously created and stored time-based media. As themedia is retrieved from storage, it is progressively transmitted as thedelivery route to the recipient is discovered, as described in detailabove.

The time-based media exchanged by the messages and/or emails is notlimited to just voice or video. In addition, the time-based media may bedelivered to a recipient in a different form than it was created. Forexample, a voice message may be transcribed into a text file or amessage in English may be translated into another language before beingdelivered to the recipient. Any media that varies over time, such assensor data, GPS or positional information, may also be transmitted.

While the invention has been particularly shown and described withreference to specific embodiments thereof, it will be understood bythose skilled in the art that changes in the form and details of thedisclosed embodiments may be made without departing from the spirit orscope of the invention. It is therefore intended that the invention beinterpreted to include all variations and equivalents that fall withinthe true spirit and scope of the invention, as provided in the attachedclaims.

What is claimed is:
 1. An application, embedded in a non-transitorytangible computer readable medium, the application includinginstructions configured to run on a mobile communication device, theapplication configured to: create a video in response to an input tocreate and send video content to a recipient using identificationinformation associated with the recipient; communicate theidentification information, to a video service available over a network,before creation of the video content of the video is complete; and startstreaming the video content of the video, while the video content iscreated using the mobile communication device, without waiting for anend-to-end connection to be first established over the network with asecond communication device associated with the recipient so that thevideo content can be at least partially rendered by the secondcommunication device while the video content is streamed by the mobilecommunication device.